home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20020314-20021006
/
000269_fdc@columbia.edu_Wed Aug 7 10:07:33 EDT 2002.msg
< prev
next >
Wrap
Text File
|
2002-10-06
|
2KB
|
54 lines
Article: 13596 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!news.columbia.edu!news-not-for-mail
From: fdc@columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Remote set file collision overwrite?
Date: 7 Aug 2002 10:06:34 -0400
Organization: Columbia University
Lines: 37
Message-ID: <air9ha$gcm$1@watsol.cc.columbia.edu>
References: <_L_39.97579$vg.3790164@bin2.nnrp.aus1.giganews.com>
NNTP-Posting-Host: watsol.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1028729195 11306 128.59.39.139 (7 Aug 2002 14:06:35 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 7 Aug 2002 14:06:35 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:13596
In article <_L_39.97579$vg.3790164@bin2.nnrp.aus1.giganews.com>,
Charles Peterson <LeslieCharles@comcast.net> wrote:
: After spot on help from you I have my client-server file transfer
: scripting working. I have one open issue.
:
: The client issues REMOTE SET FILE COLLISION OVERWRITE, as this is our
: intent. The server rejects the request with the mesg.... ?Unknown remote
: set parameter
:
The message is a bit misleading. Actually the parameter is known, but
forbidden by default to protect the server from client-initiated file
deletions. If you allow incoming files to overwrite files of the same name,
that is tantamount to allowing the client to delete files. If you wish to
allow the client to delete files, you have configure the server for it with
the command:
ENABLE DELETE
See pages 228-231 of Chapter 11.
: If I use REMOTE SET FILE COLLISION BACKUP, the existing file is backed up
: and the replaced by the new file. Not a show stopper, but does require
: subsequent clean up of the resulting .~n~ files.
:
: I also am rereading the manual to find out why it only works when throttled.
: ie client sets speed 14 and speed-matching off. Seems like we could do
: better with our boca 33.6
:
Try this on each end:
set port tapi ; Picks up modem definition from Windows.
set flow rts/cts ; Override any misconfigurations
set modem speed-matching off ; in the Windows modem database.
set speed 57600 ; Use a reasonable speed.
- Frank